Autonomous formation for backhaul networks

ABSTRACT

A user equipment (UE) may experience poor communication with a network access device, and the network access device may configure the UE to connect to, and route communications through, one or more relay nodes (e.g., which may be another UE, a network operator-deployed relay, etc.). Techniques are described whereby these relay nodes may autonomously form a wireless backhaul network. Sequential implementations are considered such that the size of the wireless backhaul network may scale efficiently. In some examples, the wireless backhaul network may form by reusing existing connectivity establishment procedures. Importantly, the proposed techniques enable a relay to possess (e.g., be configured with) functionality that may traditionally be associated with a UE, base station, and gateway. Such multi-faceted functionality may enable the described sequential formation of wireless backhaul networks with tree topology.

CROSS REFERENCES

The present application for patent claims priority to U.S. ProvisionalPatent Application No. 62/478,434 by Hampel et al., entitled “AutonomousFormation For Backhaul Networks,” filed Mar. 29, 2017, assigned to theassignee hereof.

BACKGROUND

The following relates generally to wireless communication, and morespecifically to autonomous formation for backhaul networks.

Wireless communications systems are widely deployed to provide varioustypes of communication content such as voice, video, packet data,messaging, broadcast, and so on. These systems may be capable ofsupporting communication with multiple users by sharing the availablesystem resources (e.g., time, frequency, and power). Examples of suchmultiple-access systems include code division multiple access (CDMA)systems, time division multiple access (TDMA) systems, frequencydivision multiple access (FDMA) systems, and orthogonal frequencydivision multiple access (OFDMA) systems, (e.g., a Long Term Evolution(LTE) system, or a New Radio (NR) system). A wireless multiple-accesscommunications system may include a number of base stations or accessnetwork nodes, each simultaneously supporting communication for multiplecommunication devices, which may be otherwise known as user equipment(UE).

In some cases, a UE may experience poor communication with a networkaccess device, and the network access device may configure the UE toconnect to, and route communications through, one or more relays (e.g.,which may be another UE, a network operator-deployed relay). A datarouting path between a UE and a Donor eNodeB (DeNB) may include a singlerelay node (RN) that is transparent to the UE. In some cases, however,it may be desirable for a data routing path to contain multiple suchrelays. The rollout of such highly densified networks may create abackhaul issue in the absence of wireless backhauling. Accordingly,techniques directed to multi-hop wireless backhaul networks (e.g., suchthat the data routing path between the UE and donor contains multiplerelays) may be desired. For example, such multi-hop wireless backhaulingmay be important for the rollout of millimeter wave (mmW) accesstechnologies (e.g., because the limited range of mmW-basedcommunications may result in highly densified, small-cell deployments).For the support of wireless backhauling, it may be desirable to enablenew relays to autonomously attach to already-integrated relays (e.g., byreusing existing packet data network (PDN) connectivity establishmentprocedures, and thereby obtaining network connectivity (e.g., datanetwork (DN) connectivity) to the donor).

SUMMARY

Techniques are described whereby the communication range of a wirelessdevice may be extended through the use of multiple relays, which mayautonomously form a wireless backhaul network. Such autonomously formedwireless backhaul networks may be beneficial for communications systemsthat support transmissions over frequency bands that experience largedegrees of signal attenuation or systems that would otherwise benefitfrom the expanded coverage offered by relay techniques. Additionally,these wireless backhaul networks may provide cost-efficient alternatives(or supplements) to infrastructure-based wired relay solutions.Sequential (e.g., recursive) implementations are considered such thatthe size of the wireless backhaul network may scale efficiently. In someexamples, the wireless backhaul network may be formed by reusingexisting connectivity establishment procedures. Importantly, theproposed techniques enable a relay to possess (e.g., be configured with)functionality that may traditionally be associated with a user equipment(UE), base station (BS), and gateway (GW). Such multi-facetedfunctionality may enable the described sequential formation of wirelessbackhaul networks with tree topology.

A method of wireless communication is described. The method may includeestablishing a first connection to a first data network (DN) via awireless link with a network node, receiving, from a second relay, apacket data unit (PDU) session request, forwarding the PDU sessionrequest to a network management function, identifying a DN address forthe second relay, establishing a second connection to a second DN forthe second relay, and connecting the second relay to the first DN byrouting data from the first DN to the second DN based on the identifiedDN address.

An apparatus for wireless communication is described. The apparatus mayinclude means for establishing a first connection to a first DN via awireless link with a network node, means for receiving, from a relay(e.g., a second relay), a PDU session request, means for forwarding thePDU session request to a network management function, means foridentifying a DN address for the relay (e.g., the second relay), meansfor establishing a second connection to a second DN for the relay (e.g.,the second relay), and means for connecting the relay (e.g., the secondrelay) to the first DN by routing data from the first DN to the secondDN based on the identified DN address.

Another apparatus for wireless communication is described. The apparatusmay include a processor, memory in electronic communication with theprocessor, and instructions stored in the memory. The instructions maybe operable to cause the processor to establish a first connection to afirst DN via a wireless link with a network node, receive, from a relay(e.g., a second relay), a PDU session request, forward the PDU sessionrequest to a network management function, identify a DN address for therelay (e.g., the second relay), establish a second connection to asecond DN for the relay (e.g., the second relay), and connect the relay(e.g., the second relay) to the first DN by routing data from the firstDN to the second DN based on the identified DN address.

A non-transitory computer readable medium for wireless communication isdescribed. The non-transitory computer-readable medium may includeinstructions operable to cause a processor to establish a firstconnection to a first DN via a wireless link with a network node,receive, from a relay (e.g., a second relay), a PDU session request,forward the PDU session request to a network management function,identify a DN address for the relay (e.g., the second relay), establisha second connection to a second DN for the relay (e.g., the secondrelay), and connect the relay (e.g., the second relay) to the first DNby routing data from the first DN to the second DN based on theidentified DN address.

In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, the network managementfunction resides on at least one of the network node, a core network(CN), a radio access network (RAN) node, a donor node, or an anchornode.

In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, forwarding the PDU sessionrequest includes including a gateway address of the first relay in thePDU session request. Some examples of the method, apparatus, andnon-transitory computer-readable medium described above may furtherinclude processes, features, means, or instructions for forwarding thePDU session request on the first connection.

In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, at least one of the first DNor the second DN may be one of a packet data network (PDN), an InternetProtocol (IP) network, a local area network (LAN), a backhaul network, aself-backhaul network, or a wireless multi-hop network.

In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, the first DN and the second DNmay be both one of a PDN, an IP network, a LAN, a backhaul network, aself-backhaul network, or a wireless multi-hop network.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, or instructions for receiving, from the networkmanagement function, a request to establish a gateway function for thesecond relay.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, or instructions for forwarding the data from thenetwork node to the second relay by exchanging the data between thefirst connection to the first DN and the second connection to the secondDN.

In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, establishing the secondconnection to the second DN for the second relay includes configuring atleast one data radio bearer (DRB) between the first relay and the secondrelay. Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, or instructions for forwarding data received from thenetwork node to the at least one DRB based on the identified DN address.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, or instructions for establishing a mapping between theat least one DRB and the identified DN address for the second relay.Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, or instructions for updating a forwarding informationbase (FIB) based on the mapping.

In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, the mapping may be based on acorrelation identifier (ID) associated with the second relay.

In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, identifying the DN addressincludes receiving, from the network management function, a DN addressprefix. In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, the method further comprisingdetermining the DN address for the second relay based on the DN addressprefix. Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, or instructions for transmitting the DN address to thesecond relay.

In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, the DN address includes asecond DN address prefix.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, or instructions for updating a FIB at the first relaybased on the determined DN address.

In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, the determined DN addressincludes a DN address of a set of DN addresses determined based on theDN address prefix.

In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, the identified DN address maybe preconfigured or determined via a pseudo-random function.

In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, the DN address may bedetermined based on a stateless address autoconfiguration (SLAAC).

In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, identifying the DN addressincludes transmitting, to the network node, a DN address request for thesecond relay based on the PDU session request. Some examples of themethod, apparatus, and non-transitory computer-readable medium describedabove may further include processes, features, means, or instructionsfor receiving a DN address response based on the DN address request,where the DN address response indicates the DN address for the secondrelay.

In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, the DN address requestindicates a requested DN address for the second relay.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, or instructions for updating a FIB at the first relaybased on the DN address for the second relay.

In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, identifying the DN addressincludes determining the DN address for the second relay based on thePDU session request. Some examples of the method, apparatus, andnon-transitory computer-readable medium described above may furtherinclude processes, features, means, or instructions for transmitting, tothe network node, an indication of the determined DN address for thesecond relay.

In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, establishing the secondconnection to the second DN includes receiving a first non-accessstratum (NAS) message from the second relay, the first NAS messageindicating the PDU session request. Some examples of the method,apparatus, and non-transitory computer-readable medium described abovemay further include processes, features, means, or instructions forforwarding the first NAS message to the network management function.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, or instructions for receiving, from the network node, apacket indicating the DN address for the second relay. Some examples ofthe method, apparatus, and non-transitory computer-readable mediumdescribed above may further include processes, features, means, orinstructions for transmitting the packet to the second relay.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, or instructions for receiving, from the network node,an address management message indicating a DN address management scheme,where identifying the DN address may be based on the DN addressmanagement scheme.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, or instructions for receiving, from the network node,an address management message indicating a FIB update scheme. Someexamples of the method, apparatus, and non-transitory computer-readablemedium described above may further include processes, features, means,or instructions for updating a FIB based on the FIB update scheme.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, or instructions for exchanging one or more signalingmessages between the network management function and the second relay.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, or instructions for determining packet forwarding rulesbased on the PDU session request forwarded from the second relay to thenetwork management function.

In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, establishing the firstconnection to the first DN includes transmitting, to the network node, aradio resource control (RRC) connection request message. Some examplesof the method, apparatus, and non-transitory computer-readable mediumdescribed above may further include processes, features, means, orinstructions for receiving, from the network node, an RRC responsemessage.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, or instructions for receiving, from the network node, aresponse to the PDU session request, where the response includes aCreate Session Request message.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, or instructions for identifying the DN address for thesecond relay may be based on the Create Session Request message.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, or instructions for determining a correlationidentifier (ID) for the second relay based on the Create Session Requestmessage.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, or instructions for transmitting, to the network node,a Create Session Response message indicating the correlation ID. Someexamples of the method, apparatus, and non-transitory computer-readablemedium described above may further include processes, features, means,or instructions for receiving, from the network node, a setup requestbased on the Create Session Response message.

In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, the PDU session requestindicates a network name.

In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, the DN address may include anaddress for an IP network, an 802.1 LAN, or a PDN.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a block diagram of a wireless communications system, inaccordance with various aspects of the present disclosure.

FIG. 2 illustrates an example wireless backhaul network that supportsautonomous formation for wireless backhaul networks in accordance withvarious aspects of the present disclosure.

FIGS. 3 through 6 illustrate process flows that support autonomousformation for wireless backhaul networks in accordance with variousaspects of the present disclosure.

FIGS. 7 through 9 show block diagrams of a device that supportsautonomous formation for backhaul networks in accordance with aspects ofthe present disclosure.

FIG. 10 illustrates a block diagram of a system including a UE thatsupports autonomous formation for backhaul networks in accordance withaspects of the present disclosure.

FIGS. 11 through 13 illustrate methods for autonomous formation forbackhaul networks in accordance with aspects of the present disclosure.

DETAILED DESCRIPTION

Techniques are described for transmitting a data packet between a remoteuser equipment (UE) and a network access device (e.g., a network node),core network (CN), radio access network (RAN), etc. via multiple relays.The proposed techniques allow each relay to autonomously connect to adonor (or anchor) node using a packet data unit (PDU) Session Requestprocedure that resembles the procedure used by a UE to connect to a basestation. In aspects of the present disclosure, packet data network (PDN)and data network (DN) may be used interchangeably. Further, a PDUsession may generally be understood as referring to connectivity to a DN(i.e., DN connectivity) for a UE, a group of UEs, a relay, etc. Usingthe described techniques, one or more relays may autonomously establisha wireless self-backhaul network via sequential attachment of new relaysto integrated relays. Each relay may thereby comprise UE-functionalityto request radio resource control (RRC) connection to the nextgeneration eNodeB (gNB) functionality (e.g., which may also be referredto as base station functionality) offered by a parent relay (or donor).The UE-functionality may further enable a PDU session established viathe RRC connection to the parent relay (or donor). When integrated, therelay may provide gNB functionality as well as gateway (GW)functionality to furnish child relays and/or UEs with RRC and PDUsessions. Each relay may route packets from the DN shared with itsparent (or donor) to the DN shared with its children (e.g., based on theDN address of each child).

Aspects of the disclosure are initially described in the context of awireless communications system. Aspects are then described with respectbackhaul networks and process flows. Aspects of the disclosure arefurther illustrated by and described with reference to apparatusdiagrams, system diagrams, and flowcharts that relate to autonomousformation for backhaul networks.

FIG. 1 illustrates an example of a wireless communications system 100 inaccordance with various aspects of the present disclosure. The wirelesscommunications system 100 may include network access devices 105 (e.g.,gNBs 105-a, access node controllers (ANCs) 105-b, and/or radio heads(RHs) 105-c), UEs 115, and a CN 130. The CN 130 may provide userauthentication, access authorization, tracking, Internet Protocol (IP)connectivity, and other access, routing, or mobility functions. Inaspects, the CN 130 may alternatively be referred to as, or performoperations of, a network management function as described below.Additionally or alternatively, operations of the network managementfunction may be performed by a radio access network (RAN) node, one ormore network access devices 105, or any other suitable network-operatedentity. At least some of the network access devices 105 (e.g., gNBs105-a or ANCs 105-b) may interface with the CN 130 through backhaullinks 132 (e.g., S1, S2) and may perform radio configuration andscheduling for communication with the UEs 115. In various examples, theANCs 105-b may communicate, either directly or indirectly (e.g., throughCN 130), with each other over backhaul links 134 (e.g., X1, X2), whichmay be wired or wireless communication links. Each ANC 105-b may alsocommunicate with a number of UEs 115 through a number of smart RHs(e.g., RHs 105-c).

In an alternative configuration of the wireless communications system100, the functionality of an ANC 105-b may be provided by a RH 105-c ordistributed across the RHs 105-c of an gNB 105-a. In another alternativeconfiguration of the wireless communications system 100 (e.g., a LongTerm Evolution (LTE)/LTE-Advanced (LTE-A) configuration), the RHs 105-cmay be replaced with base stations, and the ANCs 105-b may be replacedby base station controllers (or links to the CN 130). In some examples,the wireless communications system 100 may include a mix of RHs 105-c,base stations, and/or other network access devices 105 forreceiving/transmitting communications according to different radioaccess technologies (RATs) (e.g., LTE/LTE-A, 5G, Wi-Fi, etc.).

A macro cell may cover a relatively large geographic area (e.g., severalkilometers in radius) and may allow unrestricted access by UEs 115 withservice subscriptions with a network provider. A small cell may includea lower-powered RH or base station, as compared with a macro cell, andmay operate in the same or different frequency band(s) as macro cells.Small cells may include pico cells, femto cells, and micro cellsaccording to various examples. A pico cell may cover a relativelysmaller geographic area and may allow unrestricted access by UEs 115with service subscriptions with a network provider. A femto cell alsomay cover a relatively small geographic area (e.g., a home) and mayprovide restricted access by UEs 115 having an association with thefemto cell (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115for users in the home, and the like). A gNB 105-a for a macro cell maybe referred to as a macro gNB. A gNB 105-a for a small cell may bereferred to as a small cell gNB, a pico gNB, a femto gNB, or a home gNB.A gNB 105-a may support one or multiple (e.g., two, three, four, and thelike) cells.

The wireless communications system 100 may support synchronous orasynchronous operation. For synchronous operation, the gNBs 105-a and/orRHs 105-c may have similar frame timing, and transmissions fromdifferent gNBs 105-a and/or RHs 105-c may be approximately aligned intime. For asynchronous operation, the gNBs 105-a and/or RHs 105-c mayhave different frame timings, and transmissions from different gNBs105-a and/or RHs 105-c may not be aligned in time. The techniquesdescribed herein may be used for either synchronous or asynchronousoperations.

The communication networks that may accommodate some of the variousdisclosed examples may be packet-based networks that operate accordingto a layered protocol stack. In the user plane, communications at thebearer or packet data convergence protocol (PDCP) layer may be IP-based.A radio link control (RLC) layer may in some cases perform packetsegmentation and reassembly to communicate over logical channels. Amedium access control (MAC) layer may perform priority handling andmultiplexing of logical channels into transport channels. The MAC layermay also use hybrid automatic repeat request (HARD) to provideretransmission at the MAC layer to improve link efficiency. In thecontrol plane, the RRC protocol layer may provide establishment,configuration, and maintenance of an RRC connection between a UE 115 anda RH 105-c, ANC 105-b, or CN 130 supporting radio bearers for user planedata. At the Physical (PHY) layer, transport channels may be mapped tophysical channels.

The UEs 115 may be dispersed throughout the wireless communicationssystem 100, and each UE 115 may be stationary or mobile. A UE 115 mayalso include or be referred to by those skilled in the art as a mobilestation, a subscriber station, a mobile unit, a subscriber unit, awireless unit, a remote unit, a mobile device, a wireless device, awireless communications device, a remote device, a mobile subscriberstation, an access terminal, a mobile terminal, a wireless terminal, aremote terminal, a handset, a user agent, a mobile client, a client, orsome other suitable terminology. A UE 115 may be a cellular phone, apersonal digital assistant (PDA), a wireless modem, a wirelesscommunication device, a handheld device, a tablet computer, a laptopcomputer, a cordless phone, a wireless local loop (WLL) station, anInternet of Everything (IoE) device, etc. A UE 115 may be able tocommunicate with various types of gNBs 105-a, RHs 105-c, base stations,access points, or other network access devices, including macro gNBs,small cell gNBs, relay base stations, and the like. A UE 115 may also beable to communicate directly with other UEs 115 (e.g., using apeer-to-peer (P2P) protocol).

The communication links 125 shown in wireless communications system 100may include uplinks (ULs) from a UE 115 to a RH 105-c, and/or downlinks(DLs), from a RH 105-c to a UE 115. The downlinks may also be calledforward links, while the uplinks may also be called reverse links.Control information and data may be multiplexed on an uplink or downlinkaccording to various techniques. Control information and data may bemultiplexed on an uplink or downlink, for example, using time divisionmultiplexing (TDM) techniques, frequency division multiplexing (FDM)techniques, or hybrid TDM-FDM techniques.

Each communication link 125 may include one or more carriers, where eachcarrier may be a signal made up of multiple sub-carriers (e.g., waveformsignals of different frequencies) modulated according to one or moreradio access technologies. Each modulated signal may be sent on adifferent sub-carrier and may carry control information (e.g., referencesignals, control channels), overhead information, user data, etc. Thecommunication links 125 may transmit bidirectional communications usingfrequency division duplexing (FDD) techniques (e.g., using pairedspectrum resources) or time division duplexing techniques (e.g., usingunpaired spectrum resources). Frame structures for FDD (e.g., framestructure type 1) and TDD (e.g., frame structure type 2) may be defined.

In some examples of the wireless communications system 100, networkaccess devices 105 (e.g., RHs 105-c) and UEs 115 may include multipleantennas for employing antenna diversity schemes to improvecommunication quality and reliability between network access devices 105and UEs 115. Additionally or alternatively, network access devices andUEs 115 may employ multiple-input, multiple-output (MIMO) techniquesthat may take advantage of multi-path environments to transmit multiplespatial layers carrying the same or different coded data. In some cases,signal processing techniques such as beamforming (i.e., directionaltransmission) may be used with MIMO techniques to coherently combinesignal energies and overcome the path loss in specific beam directions.Precoding (e.g., weighting transmissions on different paths or layers,or from different antennas) may be used in conjunction with MIMO orbeamforming techniques.

The wireless communications system 100 may support operation on multiplecarriers, a feature which may be referred to as carrier aggregation (CA)or multi-carrier operation. A carrier may also be referred to as acomponent carrier (CC), a layer, a channel, etc. The terms “carrier,”“component carrier,” and “channel” may be used interchangeably herein. AUE 115 may be configured with multiple downlink CCs and one or moreuplink CCs for carrier aggregation. Carrier aggregation may be used withboth FDD and TDD component carriers.

In some examples, a network access device 105 may include acommunication manager 150. In some examples, the communication manager150 may include or be an example of the communications manager 715, 815,915, or 1015 described with reference to FIG. 7, 8, 9, or 10, or mayperform aspects of the methods described with reference to FIGS. 11through 13.

A 5G (or New Radio (NR)) network may have a wide spectrum and includesub-6 GigaHertz (GHz) (Sub-6G) and mmW (e.g., 30-300 GHz) bands. TheSub-6G band (or bands) currently has wider cell coverage, but the mmWband (or bands) has larger bandwidth. To fully leverage the benefits ofthe 5G mmW band(s), a dense cell deployment may be necessary (e.g.,because mmW devices typically require line-of-sight positioning forcommunication). One way to achieve a dense cell deployment is bydeploying a large number of small cells. However, such a deployment maybe costly, and may be difficult for an operator to justify in areas thatdo not have a large number of users (i.e., UEs 115). An alternative todeploying a large number of small cells is to enlist UEs 115 ascommunication relays. Additionally or alternatively, one or moreoperator-supported infrastructure-based relays may be provided. Theserelays may communicate with each other and one or more network accessdevices 105 via wireless backhaul links using techniques describedherein.

Multi-hop wireless backhaul networks, e.g. using mmW technology, enableflexible and lower cost deployments of small cells. mmW technologies areespecially well suited for extended wireless backhaul networks due totheir support of narrow antenna beams, which highly reduces inter-linkinterference. Multi-hop wireless backhauling is also important for therollout of mmW RATS. Due to the limited range of mmW-based access, mmWcells are inherently small in nature. To provide sufficient availabilityof mmW-based access to end UEs 115, highly densified small-celldeployments are necessary. The rollout of such highly densified networkscreates a backhaul problem. Since mmW-based RAT offers high linkcapacity, it is possible to integrate access (e.g., DN connectivity) andbackhaul and let mmW base stations backhaul their own access traffic inaccordance with aspects of the present disclosure. It is also possibleto support other access technologies (i.e., other than mmW) using ammW-based backhaul.

Aspects of the present disclosure allows the BS functionality of therelay to be used for the attachment of additional relays. In someexamples of the present disclosure, the relay may be capable of a GWfunction and a routing function to interconnect the DN shared with theparent relay (or donor) with the DN shared with the child relay.Further, the proposed techniques do not preclude relays from using theirBS functionality to offer UE-based access (e.g., in addition to accessfor additional relays).

FIG. 2 shows an example of a wireless backhaul network 200 that supportsautonomous formation for wireless backhaul networks in accordance withvarious aspects of the present disclosure. Wireless backhaul network 200may support communications over mmW frequencies. As described above,transmissions in mmW bands may be associated with a limited rangecoverage areas 205, such that a dense cell deployment may be employed.It is to be understood that while the present disclosure is describedwith reference to mmW transmissions, the disclosed techniques may beapplicable to any wireless communications system in which relaytechniques are beneficial. In some examples, a network node such as abase station 105, CN 130, RAN node, or other suitable wireless devicemay include or perform operations of a network management function 230.

In accordance with aspects of the present disclosure, coverage area 205associated with base station 105-b may be expanded (e.g., such that UE115-b may communicate with the CN 130-a through base station 105-b)using multi-hop relay technique. As described above, base station 105-b(e.g., which may alternatively be referred to as donor 105-b or anchor105-b) may communicate with relay 220-a via wireless backhaul 225-a. Insome examples, base station 105-b may carry additional anchor or donorfunctionality.

Relay 220-a may in turn communicate with one or more additional relays220 (e.g., relays 220-b, 220-c) via respective wireless backhauls (e.g.,wireless backhauls 225-b, 225-c). As described above, each of theserelays 220 may be a base station, an access point, a UE 115, or anyother network node. The sequential addition of relays 220 (e.g., whichmay be enabled using aspects of the present disclosure) may create themulti-hop relay tree topology described herein.

As an example, relays 220-a, 220-b, and 220-c along with base station105-b may autonomously form wireless backhaul network 200 such thatcommunications from UE 115-b may be relayed (i.e., routed) to basestation 105-b (e.g., which may serve as a proxy for CN 130-a) via relays220-a, 220-b. In aspects of the present disclosure, relay 220-a may bereferred to as a child relay with reference to base station 105-b and aparent relay with reference to relays 220-b, 220-c. Similarly, relays220-b, 220-c may be referred to as child relays with reference to relay220-a, and one or both may be a parent relay to one or more additionalrelays 220. In some cases, there may be a maximum number of relays 220supported by a single cell (e.g., associated with base station 105-b).Wireless backhaul network 200 may be autonomously established using oneor more of the techniques described below.

Interconnection between a parent relay (e.g., relay 220-a) and child(e.g., relay 220-b) may be accomplished using one or more of thefollowing steps. First, relay 220-b may send a PDU Session Request in anRRC message to relay 220-a. Relay 220-b may then receive a DN addresscontained in an RRC message from relay 220-a. Relay 220-a mayadditionally or alternatively receive an RRC connection request fromrelay 220-b, establish an RRC connection to relay 220-b, and forwardnon-access stratum (NAS) messages received on this RRC connection to CN130-a (e.g., via base station 105-b). Relay 220-a may then receive aCreate Session Request from the CN 130-a for relay 220-b, determine a DNaddress for relay 220-b, and establish the PDU session for relay 220-bbased on the determined DN address. Relay 220-a may forward datareceived on its DN connection with its parent relay (i.e., base station105-b) to the DN connection of its child (i.e., relay 220-b) based onthe determined DN address.

Because relay 220-b may act as a parent relay to another relay 220, theproposed aspects enable autonomous establishment of self-backhaulnetwork 210 via sequential attachment of additional relays 220 toalready integrated relays 220. Accordingly, each relay 220 may therebycomprise UE-functionality (i.e., to request RRC connection and a PDUsession to a parent relay) as well as BS and GW functionality to furnishchild relays 220 with RRC connectivity and PDU sessions. Each relay 220may further route packets from the PDU session shared with its parent tothe PDU session shared with its children based on the DN address(es)associated with one or more children.

FIG. 3 illustrates an example of a process flow 300 that supportsautonomous formation for backhaul networks in accordance with variousaspects of the present disclosure. Process flow 300 contains relays220-d, 220-e, 220-f, each of which may be an example of a relay 220described above. Donor 105-c may be an example of network node such as abase station 105-b and CN 130-b may be an example of the CN describedabove with reference to FIGS. 1 and 2. Data packets in process flow 300are routed via DN 330. Process flow 300 additionally contains anoperations and maintenance (OAM) server 335. In some examples describedbelow, though only one DN is illustrated for the sake of simplicity,there may be multiple DNs 330 associated with process flow 300. Althoughillustrated separately, one or more of these features may be physicallyco-located or otherwise share one or more components.

Process flow 300 illustrates a method that allows relays 220 toautonomously integrate and form a multi-hop wireless backhaul network(e.g., wireless backhaul network 200 in FIG. 2). The proposed techniquesmay leverage cellular RAT and cellular signaling procedures to establisha layer 2 (L2) link and to obtain a PDU session. Additionally, thedescribed techniques may enable wireless backhaul connectivity byinterconnecting relays 220 and donor 105-c in the backhaul network via arouting plane. Further, a sequential mechanism of relay 220 integration,where each relay 220 reciprocates similar functionality to new attachingrelays 220 as its parent relay 220 offered during its correspondingattachment, is described. This sequential mechanism may be applied tothe establishment of L2 links and PDU sessions. Further, the sequentialmechanism (in which a given type of node (e.g., a relay 220) may connectto another node of the same type (e.g., another relay 220)) representsone fundamental difference between the proposed techniques and theconventional techniques (where only one type of node (i.e., a relay 220)connects to a different type of node (i.e., a donor 105)).

Process flow 300 illustrates a sequence of activities whereby relay220-e connects to relay 220-d (i.e., as shown by block 301-a) and relay220-f subsequently connects to relay 220-e (i.e., as shown by block301-b). The signaling procedures within block 301-b may be analogous tothe corresponding procedures within block 301-a, which may demonstratethe sequential nature of the integration procedure and allows the sizeof the multi-hop wireless backhaul network to scale easily.

For the sake of simplicity, arrows within process flow 300 are referredto by the number directly above them. In some cases, multiple arrowsassociated with a given signaling process may be referred tocollectively by a single number, though it is to be understood thatthese may be separate signals (e.g., as illustrated). Additionally, thefunctionality of each relay 220 is segmented into BS, GW, and UEfunctionality for explanation purposes. It is to be understood thatthese functionalities may in some cases share one or more physical(i.e., hardware) components or otherwise overlap.

At 302, relay 220-d may establish connectivity to DN 330. Accordingly,relay 220-d may possess a DN address (e.g., prior to the operations ofblock 301-a). Relay 220-d may further support BS and GW functionality.That is, relay 220-d may be integrated into the network and have DNconnectivity. Through this DN connectivity, relay 220-d may communicatewith CN 130-b and OAM server 335. Based on these communications, relay220-d may establish BS functionality to allow additional relays 220 toattach.

The following steps 303 to 314 (i.e., block 301-a) describe theattachment of relay 220-e to relay 220-d. They may follow a connectivityprocedure in which relay 220-d holds a GW and includes a DN address forits GW into the PDU Session Request sent to the CN 130-b at 305.Accordingly, the GW of relay 220-d may be responsible for determiningthe DN address of relay 220-e, as described further below with respectto FIGS. 4 through 6.

At 303, relay 220-e may discover relay 220-d and establish an RRCconnection with relay 220-d (e.g., in the same or similar manner that aUE 115 connects to a base station 105). Accordingly, to enable 303,relay 220-e may support UE-functionality.

At 304, relay 220-e may send a PDU Session Request to relay 220-d.

At 305, relay 220-d may forward the PDU Session Request to donor 105-c,which may proxy for the CN 130-b and forward the request to the CN130-b. In some examples, relay 220-d may include its GW's DN address inthe request. Additionally or alternatively, relay 220-d may include anetwork name in the forwarded PDU Session Request.

At 306, CN 130-b may send a Create Session Request, which may beforwarded by donor 105-c to the DN address of the GW of relay 220-d. Therequest may include a request for information about relay 220-e (i.e.,the source of the PDU session request at 304).

At 307, the GW of relay 220-d may determine a DN address for relay220-e. In some examples, the GW of relay 220-d may additionally create acorrelation identifier (ID).

At 308, the GW of relay 220-d may return a Create Session Response tothe CN 130-b (e.g., with donor 105-c serving as a proxy). The CreateSession Response may include information about relay 220-e and/or acorrelation ID.

At 309, the CN 130-b may send an Initial Context Setup Request back tothe BS function on relay 220-d (e.g., via donor 105-c) including thecorrelation ID.

At 310, the BS function of relay 220-d may configure at least one dataradio bearer (DRB) with relay 220-e via an RRC ConnectionReconfiguration message, in which the BS function of relay 220-d mayinclude the DN address determined at 307.

At 311, the relay 220-d may create a mapping between the DN addressallocated for relay 220-e and the DRB to relay 220-e, and it may enterthis mapping into its forwarding information base (FIB). The correlationID (e.g., created at 307) may be used for the establishment of thismapping.

At 312, and as a result of steps 303 to 311, the UE-functionality ofrelay 220-e may obtain DN connectivity via the GW of relay 220-d. The DNconnectivity may be to the same DN 330 with which relay 220-d previouslyestablished connectivity or to another DN 330. In various examples, a DN330 may be an example of a PDN, IP network, local area network (LAN),backhaul network, self-backhaul network, or wireless multi-hop network.

At 313, using the DN connectivity obtained at 312, relay 220-e mayconnect to OAM server 335 and may obtain a configuration for BS and GWfunctionality of its own.

At 314, relay 220-e may implement the configuration obtained from OAMserver 335. In this manner, it may prepare to have new relays 220attach. The BS functionality may additionally be used for UE-basedaccess. In some cases, the BS functionality of relay 220-e may need todiscover CN 130-b. Accordingly, it may use one or more known methods(e.g., Domain Name System (DNS) request, which is resolved to the IPaddress of donor 105-c). Thus, donor 105-c may become the CN 130-b proxyfor the BS functionality of relay 220-e (e.g., in the same way that itserved as CN 130-b proxy for the BS functionality of relay 220-d).

The following steps 315 to 326 (i.e., block 301-b) describe theattachment of relay 220-f to relay 220-e. In some examples, attachmentof relay 220-f to relay 220-e may follow the same or similar proceduresas the attachment of relay 220-e to relay 220-d (i.e., block 301-a). Insome cases, relay 220-e may use the DN address obtained at 310 (i.e.,when attaching to relay 220-d) as the GW address at 317 (i.e., whenrequesting attachment of relay 220-f). Such a sequential procedure mayenable attachment of further generations of child relays 220.

At 315, relay 220-f may discover relay 220-e and establishes an RRCconnection with relay 220-e. Accordingly, to enable 315, relay 220-f maysupport UE-functionality and relay 220-e may support BS-functionality.

At 316, relay 220-f may send a PDU session request to relay 220-e.

At 317, relay 220-e may forward the PDU session request to donor 105-c,which may proxy for the CN 130-b and forward the request to the CN130-b. Relay 220-e may include its GW's DN address in the request. Insome cases, the GW DN address may be the DN address that relay 220-eobtained at 310. In some cases, relay 220-e may include a network namein the request.

At 318, CN 130-b may send a Create Session Request, which may beforwarded by donor 105-c to the DN address of the GW of relay 220-e. Therequest may include a request for information about relay 220-f (i.e.,the source of the PDU session request of 316).

At 319, the GW of relay 220-e may determine a DN address for relay220-f. In some examples, the GW of relay 220-e may additionally create acorrelation ID.

At 320, the GW of relay 220-e may return a Create Session Response tothe CN 130-b (e.g., with donor 105-c serving as a proxy). The CreateSession Response may include information about relay 220-f and/or acorrelation ID.

At 321, the CN 130-b may send an Initial Context Setup Request back tothe BS function on relay 220-e (e.g., via donor 105-c) including thecorrelation ID.

At 322, the BS function of relay 220-e may configure at least one DRBwith relay 220-f via an RRC Connection Reconfiguration message, in whichthe BS function of relay 220-e may include the DN address determined at319.

At 323, the relay 220-e may create a mapping between the DN addressallocated for relay 220-f and the DRB to relay 220-f, and it may enterthis mapping into its FIB. The correlation ID may be used for theestablishment of this mapping.

At 324, and as a result of steps 315 to 323, the UE-functionality ofrelay 220-f may obtain DN connectivity via the GW of relay 220-e. The DNconnectivity may be to the same DN 330 with which relay 220-d and/orrelay 220-e previously established connectivity or to another DN 330. Insuch instances, packets may be exchanged between a first DN (e.g., theDN to which relay 220-d established connectivity) and a second DN (towhich relay 220-e established connectivity). In various examples, a DN330 may be an example of a PDN, IP network, LAN, backhaul network,self-backhaul network, or wireless multi-hop network.

At 325, using the DN connectivity obtained at 324, relay 220-f mayconnect to OAM server 335 and may obtain a configuration for BS and GWfunctionality of its own.

At 326, relay 220-f may implement the configuration obtained from OAMserver 335. In this manner, it may prepare to have new relays 220attach. The BS functionality may additionally be used for UE-basedaccess. In some cases, the BS functionality of relay 220-f may need todiscover CN 130-b. Accordingly, it may use one or more known methods(e.g., DNS request, which is resolved to the IP address of donor 105-c).Thus, donor 105-c may become the CN 130-b proxy for the BS functionalityof relay 220-f.

Accordingly, as illustrated by process flow 300, relays 220 may attachto each other in order to build a multi-hop relay chain. Further,multiple relays 220 may attach to the same parent relay 220, therebycreating multi-hop spanning tree topologies.

In another example, the PDU session request may be handled by a networkmanagement function 230. The network management function 230 may residewithin a network node such as a CN 130-b (i.e., network managementfunction 230-b), a RAN node, donor 105-c (i.e., network managementfunction 230-a), etc. The network management function 230 may receivethe PDU session request message (e.g., at 305 or 317), send a CreateSession Request message (e.g., at 306 or 318) to the corresponding GWaddress contained in the PDU session request message, receive a PDUSession Response message from the GW (e.g., at 308 or 320) and send anInitial Context Setup Request to a BS functionality of relay 220-d orrelay 220-e (e.g., at 309 or 321), for example. Accordingly, in someexamples, process flow 300 may operate based in part on a networkmanagement function 230 which may take the role of the CN 130-b. Thenetwork management function 230 may reside at any suitable location(e.g., within CN 130-b or donor 105-c) or may be a separate entity.

In another example, relay 220-d may include a GW address in the PDUsession request at 305, and the Create Session Request at 306 may beaddressed to the GW address included in the PDU session request at 305.At 307, relay 220-d may further identify a DN address and may map the DNaddress to a correlation ID, which it may send at 308 to relay 220-e(i.e., the source of the Create Session Request at 304). The relay 220-dmay receive the correlation ID (e.g. in the Initial Context SetupRequest at 309) and may establish an L2 link with relay 220-e includingat least one DRB at 310. Relay 220-d may then allow forwarding of datapackets between the DN address identified at 307 and the L2 linkestablished with relay 220-e based on the correlation ID received at309. Similar processes may be applied to the corresponding steps ofblock 301-b (i.e., 317 to 322). Accordingly, alternatives may beconsidered in which process flow 300 operates without the use of a CN130-b (or a network management function 230, for example).

In yet another example, relay 220-e may create a second PDU Session viaa second PDU Session request message, which may coexist with the firstPDU Session created at 304 through 311. The GW used for the second PDUSession may reside at a different location from the GW used for thefirst PDU Session (e.g., it may reside outside of relay 220-d (e.g., atdonor 105-c)). Further, data exchanged on the second PDU Session may betunneled over the first PDU Session. In a variation of process flow 300,it may be possible for relay 220-e to connect to the OAM 335 via thesecond PDU Session (e.g., instead of or in addition to connecting viathe first PDU Session). The establishment of a second PDU Session mayalso be applied by relay 220-f when integrating to the network via relay220-e. The integrating relays 220 may, for instance, may use differentDN names (DNNs) when requesting establishment of the first PDU Sessionand the second PDU Session. In this manner, the parent relay 220 maydistinguish how to handle the PDU session request messages.

FIG. 4 illustrates an example of a process flow 400 that supportsautonomous formation for backhaul networks in accordance with variousaspects of the present disclosure. Process flow 400 includes networknodes such as a relay 220-g and a relay 220-h, each of which may be anexample of a relay 220 described above. In this example, relay 220-g mayrepresent a parent relay for relay 220-h. Relay 220-g may in turn be achild of another relay 220, a donor 105, or any other network node.Relay 220-h may not yet have a child relay (e.g., relay 220-h may notyet have been configured by an OAM server for BS and GW functionality).

Process flow 400 illustrates a technique for DN addressing viasequential sub-prefixing. At 405, relay 220-g may select a DN addresssub-prefix of its own prefix. That is, each relay 220 may obtain a DNaddress prefix (or set of DN addresses) from its parent relay 220instead of a single DN address. When the relay 220 (e.g., relay 220-g)has to determine a DN address prefix for an attaching child relay 220(e.g., relay 220-h), it may select a sub-prefix of its own prefix.

At 410, relay 220-g may forward the selected prefix to relay 220-h. At415, relay 220-g may enter the mapping between the selected prefix forrelay 220-h and the L2 link or one or more DRBs of relay 220-h into itsFIB table. Such an addressing scheme may lead to a hierarchical addressdistribution over the topological tree. Consequently, assignment of DNaddress prefixes for a new child relay 220 (e.g., a relay 220 attachingto relay 220-h or another relay 220 attaching to relay 220-g) may notrequire any FIB update at higher nodes of the tree.

FIG. 5 illustrates an example of a process flow 500 that supportsautonomous formation for backhaul networks in accordance with variousaspects of the present disclosure. Process flow 500 includes relay 220-iand relay 220-j, each of which may be an example of a relay 220described above. In this example, relay 220-i may represent a parentrelay for relay 220-j. Relay 220-i may in turn be a child of a networknode such as another relay 220 or donor 105-d. In the present example,relay 220-j has an attaching child relay 220 (not shown).

Process flow 500 illustrates a technique for sequential DN addressrequest/response upstream signaling. At 505, relay 220-j may send a DNaddress request upstream (i.e., towards donor 105-d) for its attachingchild relay 220. In some examples, the request may be sent as an RRCmessage to the parent relay 220 (i.e., relay 220-i), which may forwardthe request to its own parent relay 220 at 510, etc. until the DNaddress request reaches donor 105-d. Additionally or alternatively, theDN address request may be sent to donor 105-d on the data plane. Forexample, the destination address of the CN may be used in the data plane(e.g., because the donor 105-d represents the CN proxy).

Accordingly, donor 105-d may be the central address managing entity inthis approach. In some cases, address management may be performed by anetwork management function. At 515 donor 105-d may allocate a DNaddress and return it downstream via RRC messaging or data-planemessaging. The DN address response may propagate back through thebackhaul network until it reaches relay 220-j at 520. For example, theresponse message may be forwarded along the correct path in the casethat each relay 220 applies reverse-path learning based on the DNaddress request message that originated at 505 and propagated throughthe backhaul network at 510. In some cases (e.g., when the responsemessage is passed on the data plane), the response may carry the DNaddress of the destination (i.e., the DN address of the child relay 220attaching to relay 220-j).

For both RRC-based and data-plane forwarding, intermediate relays 220(e.g., relay 220-i) may update the FIB at 525 based on the new DNaddress contained in the DN address response message. This updating maybe in contrast to the example illustrated in process flow 400 in whichassignment of DN address sub-prefixes for a new child relay 220 does notrequire any FIB updating at higher nodes of the tree. In some cases(e.g., if the PDU type is IP), the Dynamic Host Configuration Protocol(DHCP) request/response mechanism may be used.

FIG. 6 illustrates an example of a process flow 600 that supportsautonomous formation for backhaul networks in accordance with variousaspects of the present disclosure. Process flow 600 includes relay 220-kand relay 220-l, each of which may be an example of a relay 220described above. In this example, relay 220-k may represent a parentrelay for relay 220-l. Relay 220-k may in turn be a child of a networknode such as another relay 220 or donor 105-e. In the present example,relay 220-l has an attaching child relay 220 (not shown).

Process flow 600 illustrates a technique for autonomous DN addressallocation with recursive address updates upstream. In this approach, anattaching child relay 220 autonomously may allocate a DN address foritself. Accordingly, at 605, relay 220-l may determine (e.g., identify)a DN address for an attaching child relay 220. This address may forinstance be provisioned (e.g., like an IEEE 802.3 hardware address) orotherwise pre-configured for the attaching child relay 220. In somecases, the attaching child relay 220 may additionally or alternativelyobtain a DN address via stateless address autoconfiguration (SLAAC)(e.g., in the case the PDU type is IPv6). The attaching child relay 220may enclose its DN address in the PDU session request message of 304 and316 described with reference to FIG. 3. As further described above, aCreate Session Request may then be passed via the CN to the GW of theparent relay 220-l. The GW of parent relay 220-l may then determine theDN address (e.g., IP address, PDN address, 802.1 (LAN address, etc.) forthe attaching child relay 220 by retrieving it from the Create SessionRequest message from the CN (e.g., described at 306 and 318 withreference to FIG. 3).

Variations to this approach may also be considered. For example, in somecases, the parent relay 220 (e.g., relay 220-l) may autonomouslydetermine the DN address for the attaching child relay 220 at 605 (e.g.,via SLAAC). After determination of the DN address for the attachingchild relay 220, relay 220-l may send a DN address update at 610 to itsown parent relay 220-k. The DN address update may propagate through thebackhaul network until it reaches donor 105-e at 615. In some cases, theDN address update that originates at 610 and propagates at 615 may usean RRC message. Intermediate relays receiving this message may updatetheir FIB at 620 based on the corresponding mapping. In anotherconsidered approach, reverse-path learning may be applied (e.g., suchthat upstream relays 220 learn the FIB mapping based on data packetssend upstream).

The techniques described above with reference to FIGS. 4 through 6 mayrepresent alternative DN address allocation (e.g., IP allocation, PDNaddress allocation, etc.) and FIB updates across the wireless backhaulnetwork when new relays 220 attach. Further alternatives to the DNaddress allocation and FIB updating beyond these examples may also beconsidered without departing from the scope of the present disclosure.For example, it may be possible that a relay 220 supports multiplealternatives for DN address management and FIB updating. To ensureinteroperability of relays 220 integrated into such a wireless backhaulnetwork, each relay 220 may be advised (e.g., via a signaling message)which of these alternatives is to be used. Such signaling may beachieved in a variety of ways. For example, the signaling may beobtained from the OAM server when configuring BS and GW routingoperations to integrate an attaching child relay 220 (e.g., as describedat 313 and 325 with reference to FIG. 3). Additionally or alternatively,the signaling may be obtained from a network node such as a donor 105(e.g., in the Create Session Request described at 306 and 318 withreference to FIG. 3). In yet another possible example, such signalingmay be obtained from the parent relay 220 (e.g., in an RRC messagedescribed at 304, 310, 316, and 322 with reference to FIG. 3). Otheralternatives and combinations are also considered.

FIG. 7 shows a block diagram 700 of a wireless device 705 that supportsautonomous formation for backhaul networks in accordance with aspects ofthe present disclosure. Wireless device 705 may be an example of aspectsof a network node such as a network access device (e.g., gNB, ANC, RH),UE, relay, or donor as described with reference to FIGS. 1 and 2.Wireless device 705 may include receiver 710, communications manager715, and transmitter 720. Wireless device 705 may also include aprocessor. Each of these components may be in communication with oneanother (e.g., via one or more buses).

Receiver 710 may receive information such as packets, user data, orcontrol information associated with various information channels (e.g.,control channels, data channels, and information related to autonomousformation for backhaul networks, etc.). Information may be passed on toother components of the device. The receiver 710 may be an example ofaspects of the transceiver 1035 described with reference to FIG. 10. Thereceiver 710 may utilize a single antenna or a set of antennas.

Communications manager 715 may be an example of aspects of thecommunications manager 1015 described with reference to FIG. 10.Communications manager 715 and/or at least some of its varioussub-components may be implemented in hardware, software executed by aprocessor, firmware, or any combination thereof. If implemented insoftware executed by a processor, the functions of the communicationsmanager 715 and/or at least some of its various sub-components may beexecuted by a general-purpose processor, a digital signal processor(DSP), an application-specific integrated circuit (ASIC), anfield-programmable gate array (FPGA) or other programmable logic device,discrete gate or transistor logic, discrete hardware components, or anycombination thereof designed to perform the functions described in thepresent disclosure.

The communications manager 715 and/or at least some of its varioussub-components may be physically located at various positions, includingbeing distributed such that portions of functions are implemented atdifferent physical locations by one or more physical devices. In someexamples, communications manager 715 and/or at least some of its varioussub-components may be a separate and distinct component in accordancewith various aspects of the present disclosure. In other examples,communications manager 715 and/or at least some of its varioussub-components may be combined with one or more other hardwarecomponents, including but not limited to an I/O component, atransceiver, a network server, another computing device, one or moreother components described in the present disclosure, or a combinationthereof in accordance with various aspects of the present disclosure.

Communications manager 715 may establish a first connection to a firstDN via a wireless link with a network node (e.g., a relay, a donor, aUE, gNB) and receive, from a second relay, a PDU session request.Communications manager 715 may further forward the PDU session requestto a network management function, identify a DN address for the secondrelay, establish a second connection to a second DN for the secondrelay, and connect the second relay to the first DN by routing data fromthe first DN to the second DN based on the identified DN address.

Transmitter 720 may transmit signals generated by other components ofthe device. In some examples, the transmitter 720 may be collocated witha receiver 710 in a transceiver module. For example, the transmitter 720may be an example of aspects of the transceiver 1035 described withreference to FIG. 10. The transmitter 720 may utilize a single antennaor a set of antennas.

FIG. 8 shows a block diagram 800 of a wireless device 805 that supportsautonomous formation for backhaul networks in accordance with aspects ofthe present disclosure. Wireless device 805 may be an example of aspectsof a wireless device 705 or a network node such as a network accessdevice (e.g., gNB, ANC, RH), UE, RN, relay, or donor as described withreference to FIGS. 1, 2, and 7. Wireless device 805 may include receiver810, communications manager 815, and transmitter 820. Wireless device805 may also include a processor. Each of these components may be incommunication with one another (e.g., via one or more buses).

Receiver 810 may receive information such as packets, user data, orcontrol information associated with various information channels (e.g.,control channels, data channels, and information related to autonomousformation for backhaul networks, etc.). Information may be passed on toother components of the device. The receiver 810 may be an example ofaspects of the transceiver 1035 described with reference to FIG. 10. Thereceiver 810 may utilize a single antenna or a set of antennas.

Communications manager 815 may be an example of aspects of thecommunications manager 1015 described with reference to FIG. 10.Communications manager 815 may also include network connection component825, reception component 830, forwarding component 835, DN component840, relay connection component 845, and data component 850.

Network connection component 825 may establish a first connection to afirst DN via a wireless link with a network node (e.g., a relay, adonor, a UE, gNB). In some cases, establishing the first connection tothe first DN may include transmitting, to the network node, an RRCconnection request message.

Reception component 830 may receive, from a second relay, a PDU sessionrequest. In some cases, reception component 830 may receive, from thenetwork management function, a request to establish a gateway functionfor the second relay. In some examples, reception component 830 mayreceive a DN address response based on the DN address request, where theDN address response indicates the DN address for the second relay.Additionally or alternatively, reception component 830 may receive, fromthe network node, a packet indicating the DN address for the secondrelay. Reception component 830 may receive, from the network node, anaddress management message indicating a DN address management scheme,where identifying the DN address may be based on the DN addressmanagement scheme. In some cases, reception component 830 may receive,from the network node, an address management message indicating a FIBupdate scheme. Reception component 830 may also receive, from thenetwork node, an RRC response message and/or receive, from the networknode, a response to the PDU session request, where the response mayinclude a Create Session Request message. In some cases, receptioncomponent 830 may receive, from the network node, a setup request basedon the Create Session Response message.

Forwarding component 835 may forward the PDU session request to anetwork management function and/or forward the PDU session request onthe first connection. In some cases, forwarding component 835 mayforward the first NAS message to the network management function anddetermine packet forwarding rules based on the PDU session requestforwarded from the second relay to the network management function. Insome cases, the network management function may reside on at least oneof the network node, a CN, a RAN node, a donor node, or an anchor node.In some examples, forwarding the PDU session request may compriseincluding a gateway address of the first relay in the PDU sessionrequest. In some cases, the PDU session request may indicate a networkname (e.g., a DNN).

DN component 840 may identify a DN address for the second relay,transmit the DN address to the second relay, and identify the DN addressfor the second relay (e.g., based on a Create Session Request message).In some cases, at least one of the first DN or the second DN may be oneof a PDN, an IP network, a LAN, a backhaul network, a self-backhaulnetwork, or a wireless multi-hop network. In some examples, the DNaddress may include an address for an IP network, an 802.1 LAN, or aPDN. In some aspects, the first DN and the second DN may be both one ofa PDN, an IP network, a LAN, a backhaul network, a self-backhaulnetwork, or a wireless multi-hop network (e.g., the first DN and secondDN may be the same type of data network). In some cases, identifying theDN address may include receiving, from the network management function,a DN address prefix. In some instances, the method may further includedetermining the DN address for the second relay based on the DN addressprefix. In some cases, the DN address may include a second DN addressprefix. In some examples, the identified DN address may be preconfiguredor determined via a pseudo-random function. In some instances, the DNaddress may be determined based on a SLAAC. In some aspects, identifyingthe DN address may include transmitting, to the network node, a DNaddress request for the second relay based on the PDU session request.In some cases, the DN address request may indicate a requested DNaddress for the second relay. In some examples, identifying the DNaddress may include determining the DN address for the second relaybased on the PDU session request. In some instances, the determined DNaddress may include a DN address of a set of DN addresses determinedbased on the DN address prefix.

Relay connection component 845 may establish a second connection to asecond DN for the second relay. In some cases, establishing the secondconnection to the second DN for the second relay may include configuringat least one DRB between the first relay and the second relay. In someaspects, establishing the second connection to the second DN may includereceiving a first NAS message from the second relay, the first NASmessage indicating the PDU session request.

Data component 850 may connect the second relay to the first DN byrouting data from the first DN to the second DN based on the identifiedDN address. Data component 850 may forward the data from the networknode to the second relay by exchanging the data between the firstconnection to the first DN and the second connection to the second DNand forward data received from the network node to the at least one DRBbased on the identified DN address.

Transmitter 820 may transmit signals generated by other components ofthe device. In some examples, the transmitter 820 may be collocated witha receiver 810 in a transceiver module. For example, the transmitter 820may be an example of aspects of the transceiver 1035 described withreference to FIG. 10. The transmitter 820 may utilize a single antennaor a set of antennas.

FIG. 9 shows a block diagram 900 of a communications manager 915 thatsupports autonomous formation for backhaul networks in accordance withaspects of the present disclosure. The communications manager 915 may bean example of aspects of a communications manager 715, a communicationsmanager 815, or a communications manager 1015 described with referenceto FIGS. 7, 8, and 10. The communications manager 915 may includenetwork connection component 920, reception component 925, forwardingcomponent 930, DN component 935, relay connection component 940, datacomponent 945, mapping component 950, FIB component 955, transmissioncomponent 960, exchange component 965, and correlation component 970.Each of these modules may communicate, directly or indirectly, with oneanother (e.g., via one or more buses).

Network connection component 920 may establish a first connection to afirst DN via a wireless link with a network node (e.g., a relay, adonor, a UE, gNB). In some cases, establishing the first connection tothe first DN may include transmitting, to the network node, a RRCconnection request message.

Reception component 925 may receive, from a second relay, a PDU sessionrequest. Reception component 925 may receive, from the networkmanagement function, a request to establish a gateway function for thesecond relay. Reception component 925 may receive a DN address responsebased on the DN address request, where the DN address response mayindicate the DN address for the second relay. Reception component 925may additionally or alternatively receive, from the network node, apacket indicating the DN address for the second relay. Receptioncomponent 925 may receive, from the network node, an address managementmessage indicating a DN address management scheme, where identifying theDN address may be based on the DN address management scheme. Receptioncomponent 925 may receive, from the network node, an address managementmessage indicating a FIB update scheme. In some examples, receptioncomponent 925 may receive, from the network node, an RRC responsemessage. Reception component 925 may receive, from the network node, aresponse to the PDU session request, where the response may include aCreate Session Request message. Reception component 925 may receive,from the network node, a setup request based on the Create SessionResponse message.

Forwarding component 930 may forward the PDU session request to anetwork management function. Forwarding component 930 may forward thePDU session request on the first connection. Forwarding component 930may forward the first NAS message to the network management function,and determine packet forwarding rules based on the PDU session requestforwarded from the second relay to the network management function. Insome cases, the network management function may reside on at least oneof the network node, a CN, a RAN node, a donor node, or an anchor node.In some cases, forwarding the PDU session request may involve includinga gateway address of the first relay in the PDU session request. In somecases, the PDU session request may indicate a network name.

DN component 935 may identify a DN address for the second relay. DNcomponent 935 may transmit the DN address to the second relay andidentify the DN address for the second relay based on the Create SessionRequest message. In some cases, the DN address may include an addressfor an IP network, an 802.1 LAN, or a PDN. In some examples, at leastone of the first DN or the second DN may be one of a PDN, an IP network,a LAN, a backhaul network, a self-backhaul network, or a wirelessmulti-hop network. In some instances, the first DN and the second DN maybe both one of a PDN, an IP network, a LAN, a backhaul network, aself-backhaul network, or a wireless multi-hop network. In some aspects,identifying the DN address may include receiving, from the networkmanagement function, a DN address prefix. In some cases, determining theDN address for the second relay may be based on the DN address prefix.In some examples, the DN address may include a second DN address prefix.In some instances, at least one of the first DN or the second DN may beone of a PDN, an IP network, a LAN, a backhaul network, a self-backhaulnetwork, or a wireless multi-hop network. In some aspects, theidentified DN address may be preconfigured or determined via apseudo-random function. In some cases, the DN address may be determinedbased on a SLAAC. In some examples, identifying the DN address mayinclude transmitting, to the network node, a DN address request for thesecond relay based on the PDU session request. In some instances, the DNaddress request may indicate a requested DN address for the secondrelay. In some aspects, identifying the DN address may includedetermining the DN address for the second relay based on the PDU sessionrequest. In some cases, the determined DN address may include a DNaddress of a set of DN addresses determined based on the DN addressprefix.

Relay connection component 940 may establish a second connection to asecond DN for the second relay. In some cases, establishing the secondconnection to the second DN for the second relay may include configuringat least one DRB between the first relay and the second relay. In someexamples, establishing the second connection to the second DN mayinclude receiving a first NAS message from the second relay, the firstNAS message indicating the PDU session request.

Data component 945 may connect the second relay to the first DN byrouting data from the first DN to the second DN based on the identifiedDN address. Data component 945 may forward the data from the networknode to the second relay by exchanging the data between the firstconnection to the first DN and the second connection to the second DNand forward data received from the network node to the at least one DRBbased on the identified DN address.

Mapping component 950 may establish a mapping between the at least oneDRB and the identified DN address for the second relay. In some cases,the mapping may be based on a correlation ID associated with the secondrelay.

FIB component 955 may update a FIB based on the mapping, update a FIB atthe first relay based on the determined DN address. FIB component 955may update a FIB at the first relay based on the DN address for thesecond relay and update a FIB based on the FIB update scheme.

Transmission component 960 may transmit, to the network node, anindication of the determined DN address for the second relay.Transmission component 960 may transmit the packet to the second relay,and transmit, to the network node, a Create Session Response messageindicating the correlation ID.

Exchange component 965 may exchange one or more signaling messagesbetween the network management function and the second relay.

Correlation component 970 may determine a correlation ID for the secondrelay based on the Create Session Request message.

FIG. 10 shows a diagram of a system 1000 including a device 1005 thatsupports autonomous formation for backhaul networks in accordance withaspects of the present disclosure. Device 1005 may be an example of orinclude the components of wireless device 705, wireless device 805, or anetwork node such as a network access device (e.g., gNB, ANC, RH), UE,RN, relay, or donor, as described above, e.g., with reference to FIGS.1, 7 and 8. Device 1005 may include components for bi-directional voiceand data communications including components for transmitting andreceiving communications, including communications manager 1015,processor 1020, memory 1025, software 1030, transceiver 1035, antenna1040, and I/O controller 1045. These components may be in electroniccommunication via one or more busses (e.g., bus 1010).

Processor 1020 may include an intelligent hardware device, (e.g., ageneral-purpose processor, a DSP, a central processing unit (CPU), amicrocontroller, an ASIC, an FPGA, a programmable logic device, adiscrete gate or transistor logic component, a discrete hardwarecomponent, or any combination thereof). In some cases, processor 1020may be configured to operate a memory array using a memory controller.In other cases, a memory controller may be integrated into processor1020. Processor 1020 may be configured to execute computer-readableinstructions stored in a memory to perform various functions (e.g.,functions or tasks supporting autonomous formation for backhaulnetworks).

Memory 1025 may include random access memory (RAM) and read only memory(ROM). The memory 1025 may store computer-readable, computer-executablesoftware 1030 including instructions that, when executed, cause theprocessor to perform various functions described herein. In some cases,the memory 1025 may contain, among other things, a basic input/outputsystem (BIOS) which may control basic hardware and/or software operationsuch as the interaction with peripheral components or devices.

Software 1030 may include code to implement aspects of the presentdisclosure, including code to support autonomous formation for backhaulnetworks. Software 1030 may be stored in a non-transitorycomputer-readable medium such as system memory or other memory. In somecases, the software 1030 may not be directly executable by the processorbut may cause a computer (e.g., when compiled and executed) to performfunctions described herein.

Transceiver 1035 may communicate bi-directionally, via one or moreantennas, wired, or wireless links as described above. For example, thetransceiver 1035 may represent a wireless transceiver and maycommunicate bi-directionally with another wireless transceiver. Thetransceiver 1035 may also include a modem to modulate the packets andprovide the modulated packets to the antennas for transmission, and todemodulate packets received from the antennas.

In some cases, the wireless device may include a single antenna 1040.However, in some cases the device may have more than one antenna 1040,which may be capable of concurrently transmitting or receiving multiplewireless transmissions.

I/O controller 1045 may manage input and output signals for device 1005.I/O controller 1045 may also manage peripherals not integrated intodevice 1005. In some cases, I/O controller 1045 may represent a physicalconnection or port to an external peripheral. In some cases, I/Ocontroller 1045 may utilize an operating system such as iOS®, ANDROID®,MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, or another known operatingsystem. In other cases, I/O controller 1045 may represent or interactwith a modem, a keyboard, a mouse, a touchscreen, or a similar device.In some cases, I/O controller 1045 may be implemented as part of aprocessor. In some cases, a user may interact with device 1005 via I/Ocontroller 1045 or via hardware components controlled by I/O controller1045.

FIG. 11 shows a flowchart illustrating a method 1100 for autonomousformation for backhaul networks in accordance with aspects of thepresent disclosure. The operations of method 1100 may be implemented bya network node such as a network access device (e.g., gNB, ANC, RH), UE,RN, relay, or donor or its components as described herein. For example,the operations of method 1100 may be performed by a communicationsmanager as described with reference to FIGS. 7 through 10. In someexamples, a network node such as a network access device (e.g., gNB,ANC, RH), UE, relay, or donor may execute a set of codes to control thefunctional elements of the device to perform the functions describedbelow. Additionally or alternatively, the network node such as a networkaccess device (e.g., gNB, ANC, RH), UE, relay, or donor may performaspects of the functions described below using special-purpose hardware.

At block 1105 the network node such as a network access device (e.g.,gNB, ANC, RH), UE, relay, or donor may establish a first connection to afirst DN via a wireless link with a network node. The operations ofblock 1105 may be performed according to the methods described withreference to FIGS. 1 through 6. In certain examples, aspects of theoperations of block 1105 may be performed by a network connectioncomponent as described with reference to FIGS. 7 through 10.

At block 1110 the network node such as a network access device (e.g.,gNB, ANC, RH), UE, relay, or donor may receive, from a second relay, aPDU session request. The operations of block 1110 may be performedaccording to the methods described with reference to FIGS. 1 through 6.In certain examples, aspects of the operations of block 1110 may beperformed by a reception component as described with reference to FIGS.7 through 10.

At block 1115 the network node such as a network access device (e.g.,gNB, ANC, RH), UE, relay, or donor may forward the PDU session requestto a network management function. The operations of block 1115 may beperformed according to the methods described with reference to FIGS. 1through 6. In certain examples, aspects of the operations of block 1115may be performed by a forwarding component as described with referenceto FIGS. 7 through 10.

At block 1120 the network node such as a network access device (e.g.,gNB, ANC, RH), UE, relay, or donor may identify a DN address for thesecond relay. The operations of block 1120 may be performed according tothe methods described with reference to FIGS. 1 through 6. In certainexamples, aspects of the operations of block 1120 may be performed by aDN component as described with reference to FIGS. 7 through 10.

At block 1125 the network node such as a network access device (e.g.,gNB, ANC, RH), UE, relay, or donor may establish a second connection toa second DN for the second relay. The operations of block 1125 may beperformed according to the methods described with reference to FIGS. 1through 6. In certain examples, aspects of the operations of block 1125may be performed by a relay connection component as described withreference to FIGS. 7 through 10.

At block 1130 the network node such as a network access device (e.g.,gNB, ANC, RH), UE, relay, or donor may connect the second relay to thefirst DN by routing data from the first DN to the second DN based atleast in part on the identified DN address. The operations of block 1130may be performed according to the methods described with reference toFIGS. 1 through 6. In certain examples, aspects of the operations ofblock 1130 may be performed by a data component as described withreference to FIGS. 7 through 10.

FIG. 12 shows a flowchart illustrating a method 1200 for autonomousformation for backhaul networks in accordance with aspects of thepresent disclosure. The operations of method 1200 may be implemented bya network node such as a network access device (e.g., gNB, ANC, RH), UE,relay, or donor or its components as described herein. For example, theoperations of method 1200 may be performed by a communications manageras described with reference to FIGS. 7 through 10. In some examples, anetwork node such as a network access device (e.g., gNB, ANC, RH), UE,relay, or donor may execute a set of codes to control the functionalelements of the device to perform the functions described below.Additionally or alternatively, the network node such as a network accessdevice (e.g., gNB, ANC, RH), UE, relay, or donor may perform aspects ofthe functions described below using special-purpose hardware.

At block 1205 the network node such as a network access device (e.g.,gNB, ANC, RH), UE, relay, or donor may establish a first connection to afirst DN via a wireless link with a network node. The operations ofblock 1205 may be performed according to the methods described withreference to FIGS. 1 through 6. In certain examples, aspects of theoperations of block 1205 may be performed by a network connectioncomponent as described with reference to FIGS. 7 through 10.

At block 1210 the network node such as a network access device (e.g.,gNB, ANC, RH), UE, relay, or donor may receive, from a second relay, aPDU session request. The operations of block 1210 may be performedaccording to the methods described with reference to FIGS. 1 through 6.In certain examples, aspects of the operations of block 1210 may beperformed by a reception component as described with reference to FIGS.7 through 10.

At block 1215 the network node such as a network access device (e.g.,gNB, ANC, RH), UE, relay, or donor may forward the PDU session requestto a network management function. The operations of block 1215 may beperformed according to the methods described with reference to FIGS. 1through 6. In certain examples, aspects of the operations of block 1215may be performed by a forwarding component as described with referenceto FIGS. 7 through 10.

At block 1220 the network node such as a network access device (e.g.,gNB, ANC, RH), UE, relay, or donor may identify a DN address for thesecond relay. The operations of block 1220 may be performed according tothe methods described with reference to FIGS. 1 through 6. In certainexamples, aspects of the operations of block 1220 may be performed by aDN component as described with reference to FIGS. 7 through 10.

At block 1225 the network node such as a network access device (e.g.,gNB, ANC, RH), UE, relay, or donor may establish a second connection toa second DN for the second relay. The operations of block 1225 may beperformed according to the methods described with reference to FIGS. 1through 6. In certain examples, aspects of the operations of block 1225may be performed by a relay connection component as described withreference to FIGS. 7 through 10.

At block 1230 the network node such as a network access device (e.g.,gNB, ANC, RH), UE, relay, or donor may connect the second relay to thefirst DN by routing data from the first DN to the second DN based atleast in part on the identified DN address. The operations of block 1230may be performed according to the methods described with reference toFIGS. 1 through 6. In certain examples, aspects of the operations ofblock 1230 may be performed by a data component as described withreference to FIGS. 7 through 10.

At block 1235 the network node such as a network access device (e.g.,gNB, ANC, RH), UE, relay, or donor may forward the data from the networknode to the second relay by exchanging the data between the firstconnection to the first DN and the second connection to the second DN.The operations of block 1235 may be performed according to the methodsdescribed with reference to FIGS. 1 through 6. In certain examples,aspects of the operations of block 1235 may be performed by a datacomponent as described with reference to FIGS. 7 through 10.

FIG. 13 shows a flowchart illustrating a method 1300 for autonomousformation for backhaul networks in accordance with aspects of thepresent disclosure. The operations of method 1300 may be implemented bya network node such as a network access device (e.g., gNB, ANC, RH), UE,relay, or donor or its components as described herein. For example, theoperations of method 1300 may be performed by a communications manageras described with reference to FIGS. 7 through 10. In some examples, anetwork node such as a network access device (e.g., gNB, ANC, RH), UE,relay, or donor may execute a set of codes to control the functionalelements of the device to perform the functions described below.Additionally or alternatively, the network node such as a network accessdevice (e.g., gNB, ANC, RH), UE, relay, or donor may perform aspects ofthe functions described below using special-purpose hardware.

At block 1305 the network node such as a network access device (e.g.,gNB, ANC, RH), UE, relay, or donor may establish a first connection to afirst DN via a wireless link with a network node. The operations ofblock 1305 may be performed according to the methods described withreference to FIGS. 1 through 6. In certain examples, aspects of theoperations of block 1305 may be performed by a network connectioncomponent as described with reference to FIGS. 7 through 10.

At block 1310 the network node such as a network access device (e.g.,gNB, ANC, RH), UE, relay, or donor may receive, from a second relay, aPDU session request. The operations of block 1310 may be performedaccording to the methods described with reference to FIGS. 1 through 6.In certain examples, aspects of the operations of block 1310 may beperformed by a reception component as described with reference to FIGS.7 through 10.

At block 1315 the network node such as a network access device (e.g.,gNB, ANC, RH), UE, relay, or donor may forward the PDU session requestto a network management function. The operations of block 1315 may beperformed according to the methods described with reference to FIGS. 1through 6. In certain examples, aspects of the operations of block 1315may be performed by a forwarding component as described with referenceto FIGS. 7 through 10.

At block 1320 the network node such as a network access device (e.g.,gNB, ANC, RH), UE, relay, or donor may identify a DN address for thesecond relay. The operations of block 1320 may be performed according tothe methods described with reference to FIGS. 1 through 6. In certainexamples, aspects of the operations of block 1320 may be performed by aDN component as described with reference to FIGS. 7 through 10.

At block 1325 the network node such as a network access device (e.g.,gNB, ANC, RH), UE, relay, or donor may establish a second connection toa second DN for the second relay. The operations of block 1325 may beperformed according to the methods described with reference to FIGS. 1through 6. In certain examples, aspects of the operations of block 1325may be performed by a relay connection component as described withreference to FIGS. 7 through 10.

At block 1330 the network node such as a network access device (e.g.,gNB, ANC, RH), UE, relay, or donor may connect the second relay to thefirst DN by routing data from the first DN to the second DN based atleast in part on the identified DN address. The operations of block 1330may be performed according to the methods described with reference toFIGS. 1 through 6. In certain examples, aspects of the operations ofblock 1330 may be performed by a data component as described withreference to FIGS. 7 through 10.

At block 1335 the network node such as a network access device (e.g.,gNB, ANC, RH), UE, relay, or donor may receive, from the network node, apacket indicating the DN address for the second relay. The operations ofblock 1335 may be performed according to the methods described withreference to FIGS. 1 through 6. In certain examples, aspects of theoperations of block 1335 may be performed by a reception component asdescribed with reference to FIGS. 7 through 10.

At block 1340 the network node such as a network access device (e.g.,gNB, ANC, RH), UE, relay, or donor may transmit the packet to the secondrelay. The operations of block 1340 may be performed according to themethods described with reference to FIGS. 1 through 6. In certainexamples, aspects of the operations of block 1340 may be performed by atransmission component as described with reference to FIGS. 7 through10.

It should be noted that the methods described above describe possibleimplementations, and that the operations and the steps may be rearrangedor otherwise modified and that other implementations are possible.Further, aspects from two or more of the methods may be combined.

Techniques described herein may be used for various wirelesscommunications systems such as code division multiple access (CDMA),time division multiple access (TDMA), frequency division multiple access(FDMA), orthogonal frequency division multiple access (OFDMA), singlecarrier frequency division multiple access (SC-FDMA), and other systems.The terms “system” and “network” are often used interchangeably. A CDMAsystem may implement a radio technology such as CDMA2000, UniversalTerrestrial Radio Access (UTRA), etc. CDMA2000 covers IS-2000, IS-95,and IS-856 standards. IS-2000 Releases may be commonly referred to asCDMA2000 1×, 1×, etc. IS-856 (TIA-856) is commonly referred to asCDMA2000 1×EV-DO, High Rate Packet Data (HRPD), etc. UTRA includesWideband CDMA (WCDMA) and other variants of CDMA. A TDMA system mayimplement a radio technology such as Global System for MobileCommunications (GSM).

An OFDMA system may implement a radio technology such as Ultra MobileBroadband (UMB), Evolved UTRA (E-UTRA), Institute of Electrical andElectronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE802.20, Flash-OFDM, etc. UTRA and E-UTRA are part of Universal MobileTelecommunications System (UMTS). LTE and LTE-A are releases of UMTSthat use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, NR, and GSM aredescribed in documents from the organization named “3rd GenerationPartnership Project” (3GPP). CDMA2000 and UMB are described in documentsfrom an organization named “3rd Generation Partnership Project 2”(3GPP2). The techniques described herein may be used for the systems andradio technologies mentioned above as well as other systems and radiotechnologies. While aspects of an LTE or an NR system may be describedfor purposes of example, and LTE or NR terminology may be used in muchof the description, the techniques described herein are applicablebeyond LTE or NR applications.

In LTE/LTE-A networks, including such networks described herein, theterm evolved node B (eNB) may be generally used to describe the basestations. The wireless communications system or systems described hereinmay include a heterogeneous LTE/LTE-A or NR network in which differenttypes of eNBs provide coverage for various geographical regions. Forexample, each eNB, next generation NodeB (gNB), or base station mayprovide communication coverage for a macro cell, a small cell, or othertypes of cell. The term “cell” may be used to describe a base station, acarrier or component carrier associated with a base station, or acoverage area (e.g., sector, etc.) of a carrier or base station,depending on context.

Base stations may include or may be referred to by those skilled in theart as a base transceiver station, a radio base station, an accesspoint, a radio transceiver, a NodeB, eNB, gNB, Home NodeB, a HomeeNodeB, or some other suitable terminology. The geographic coverage areafor a base station may be divided into sectors making up only a portionof the coverage area. The wireless communications system or systemsdescribed herein may include base stations of different types (e.g.,macro or small cell base stations). The UEs described herein may be ableto communicate with various types of base stations and network equipmentincluding macro eNBs, small cell eNBs, gNBs, relay base stations, andthe like. There may be overlapping geographic coverage areas fordifferent technologies.

A macro cell generally covers a relatively large geographic area (e.g.,several kilometers in radius) and may allow unrestricted access by UEswith service subscriptions with the network provider. A small cell is alower-powered base station, as compared with a macro cell, that mayoperate in the same or different (e.g., licensed, unlicensed, etc.)frequency bands as macro cells. Small cells may include pico cells,femto cells, and micro cells according to various examples. A pico cell,for example, may cover a small geographic area and may allowunrestricted access by UEs with service subscriptions with the networkprovider. A femto cell may also cover a small geographic area (e.g., ahome) and may provide restricted access by UEs having an associationwith the femto cell (e.g., UEs in a closed subscriber group (CSG), UEsfor users in the home, and the like). An eNB for a macro cell may bereferred to as a macro eNB. An eNB for a small cell may be referred toas a small cell eNB, a pico eNB, a femto eNB, or a home eNB. An eNB maysupport one or multiple (e.g., two, three, four, and the like) cells(e.g., component carriers).

The wireless communications system or systems described herein maysupport synchronous or asynchronous operation. For synchronousoperation, the base stations may have similar frame timing, andtransmissions from different base stations may be approximately alignedin time. For asynchronous operation, the base stations may havedifferent frame timing, and transmissions from different base stationsmay not be aligned in time. The techniques described herein may be usedfor either synchronous or asynchronous operations.

The downlink transmissions described herein may also be called forwardlink transmissions while the uplink transmissions may also be calledreverse link transmissions. Each communication link describedherein—including, for example, wireless communications system 100 and200 of FIGS. 1 and 2—may include one or more carriers, where eachcarrier may be a signal made up of multiple sub-carriers (e.g., waveformsignals of different frequencies).

The description set forth herein, in connection with the appendeddrawings, describes example configurations and does not represent allthe examples that may be implemented or that are within the scope of theclaims. The term “exemplary” used herein means “serving as an example,instance, or illustration,” and not “preferred” or “advantageous overother examples.” The detailed description includes specific details forthe purpose of providing an understanding of the described techniques.These techniques, however, may be practiced without these specificdetails. In some instances, well-known structures and devices are shownin block diagram form in order to avoid obscuring the concepts of thedescribed examples.

In the appended figures, similar components or features may have thesame reference label. Further, various components of the same type maybe distinguished by following the reference label by a dash and a secondlabel that distinguishes among the similar components. If just the firstreference label is used in the specification, the description isapplicable to any one of the similar components having the same firstreference label irrespective of the second reference label.

Information and signals described herein may be represented using any ofa variety of different technologies and techniques. For example, data,instructions, commands, information, signals, bits, symbols, and chipsthat may be referenced throughout the above description may berepresented by voltages, currents, electromagnetic waves, magneticfields or particles, optical fields or particles, or any combinationthereof.

The various illustrative blocks and modules described in connection withthe disclosure herein may be implemented or performed with ageneral-purpose processor, a DSP, an ASIC, an FPGA or other programmablelogic device, discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. A general-purpose processor may be a microprocessor,but in the alternative, the processor may be any conventional processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices (e.g., a combinationof a DSP and a microprocessor, multiple microprocessors, one or moremicroprocessors in conjunction with a DSP core, or any other suchconfiguration).

The functions described herein may be implemented in hardware, softwareexecuted by a processor, firmware, or any combination thereof. Ifimplemented in software executed by a processor, the functions may bestored on or transmitted over as one or more instructions or code on acomputer-readable medium. Other examples and implementations are withinthe scope of the disclosure and appended claims. For example, due to thenature of software, functions described above can be implemented usingsoftware executed by a processor, hardware, firmware, hardwiring, orcombinations of any of these. Features implementing functions may alsobe physically located at various positions, including being distributedsuch that portions of functions are implemented at different physicallocations. Also, as used herein, including in the claims, “or” as usedin a list of items (for example, a list of items prefaced by a phrasesuch as “at least one of” or “one or more of”) indicates an inclusivelist such that, for example, a list of at least one of A, B, or C meansA or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, asused herein, the phrase “based on” shall not be construed as a referenceto a closed set of conditions. For example, an exemplary step that isdescribed as “based on condition A” may be based on both a condition Aand a condition B without departing from the scope of the presentdisclosure. In other words, as used herein, the phrase “based on” shallbe construed in the same manner as the phrase “based at least in parton.”

Computer-readable media includes both non-transitory computer storagemedia and communication media including any medium that facilitatestransfer of a computer program from one place to another. Anon-transitory storage medium may be any available medium that can beaccessed by a general purpose or special purpose computer. By way ofexample, and not limitation, non-transitory computer-readable media maycomprise RAM, ROM, electrically erasable programmable read only memory(EEPROM), compact disk (CD) ROM or other optical disk storage, magneticdisk storage or other magnetic storage devices, or any othernon-transitory medium that can be used to carry or store desired programcode means in the form of instructions or data structures and that canbe accessed by a general-purpose or special-purpose computer, or ageneral-purpose or special-purpose processor. Also, any connection isproperly termed a computer-readable medium. For example, if the softwareis transmitted from a website, server, or other remote source using acoaxial cable, fiber optic cable, twisted pair, digital subscriber line(DSL), or wireless technologies such as infrared, radio, and microwave,then the coaxial cable, fiber optic cable, twisted pair, DSL, orwireless technologies such as infrared, radio, and microwave areincluded in the definition of medium. Disk and disc, as used herein,include CD, laser disc, optical disc, digital versatile disc (DVD),floppy disk and Blu-ray disc where disks usually reproduce datamagnetically, while discs reproduce data optically with lasers.Combinations of the above are also included within the scope ofcomputer-readable media.

The description herein is provided to enable a person skilled in the artto make or use the disclosure. Various modifications to the disclosurewill be readily apparent to those skilled in the art, and the genericprinciples defined herein may be applied to other variations withoutdeparting from the scope of the disclosure. Thus, the disclosure is notlimited to the examples and designs described herein, but is to beaccorded the broadest scope consistent with the principles and novelfeatures disclosed herein.

What is claimed is:
 1. A method for wireless communication at a firstrelay, comprising: establishing a first connection to a first datanetwork (DN) via a wireless link with a network node; receiving, from asecond relay, a packet data unit (PDU) session request; forwarding thePDU session request to a network management function; identifying a DNaddress for the second relay; establishing a second connection to asecond DN for the second relay; and connecting the second relay to thefirst DN by routing data from the first DN to the second DN based atleast in part on the identified DN address.
 2. The method of claim 1,wherein the network management function resides on at least one of thenetwork node, a core network node, a radio access network (RAN) node, adonor node, or an anchor node.
 3. The method of claim 1, whereinforwarding the PDU session request comprises: including a gatewayaddress of the first relay in the PDU session request; and forwardingthe PDU session request on the first connection.
 4. The method of claim1, wherein at least one of the first DN or the second DN is one of apacket data network (PDN), an Internet Protocol (IP) network, a localarea network (LAN), a backhaul network, a self-backhaul network, or awireless multi-hop network.
 5. The method of claim 1, furthercomprising: receiving, from the network management function, a requestto establish a gateway function for the second relay.
 6. The method ofclaim 1, further comprising: forwarding the data from the network nodeto the second relay by exchanging the data between the first connectionto the first DN and the second connection to the second DN.
 7. Themethod of claim 1, wherein establishing the second connection to thesecond DN for the second relay comprises: configuring at least one dataradio bearer (DRB) between the first relay and the second relay; andforwarding data received from the network node to the at least one DRBbased on the identified DN address.
 8. The method of claim 7, furthercomprising: establishing a mapping between the at least one DRB and theidentified DN address for the second relay; and updating a forwardinginformation base (FIB) based at least in part on the mapping.
 9. Themethod of claim 8, wherein the mapping is based at least in part on acorrelation identifier (ID) associated with the second relay.
 10. Themethod of claim 1, wherein identifying the DN address comprises:receiving, from the network management function, a DN address prefix;the method further comprising determining the DN address for the secondrelay based at least in part on the DN address prefix; and transmittingthe DN address to the second relay.
 11. The method of claim 10, furthercomprising: updating a forwarding information base (FIB) at the firstrelay based at least in part on the determined DN address.
 12. Themethod of claim 10, wherein the determined DN address comprises a DNaddress of a set of DN addresses determined based at least in part onthe DN address prefix.
 13. The method of claim 1, wherein the identifiedDN address is preconfigured or determined via a pseudo-random function.14. The method of claim 13, wherein the DN address is determined basedat least in part on a stateless address autoconfiguration (SLAAC). 15.The method of claim 1, wherein identifying the DN address comprises:transmitting, to the network node, a DN address request for the secondrelay based at least in part on the PDU session request; and receiving aDN address response based at least in part on the DN address request,wherein the DN address response indicates the DN address for the secondrelay.
 16. The method of claim 15, wherein the DN address requestindicates a requested DN address for the second relay.
 17. The method ofclaim 15, further comprising: updating a forwarding information base(FIB) at the first relay based at least in part on the DN address forthe second relay.
 18. The method of claim 1, wherein identifying the DNaddress comprises: determining the DN address for the second relay basedat least in part on the PDU session request; and transmitting, to thenetwork node, an indication of the determined DN address for the secondrelay.
 19. The method of claim 1, wherein establishing the secondconnection to the second DN comprises: receiving a first non-accessstratum (NAS) message from the second relay, the first NAS messageindicating the PDU session request; and forwarding the first NAS messageto the network management function.
 20. The method of claim 1, furthercomprising: receiving, from the network node, a packet indicating the DNaddress for the second relay; and transmitting the packet to the secondrelay.
 21. The method of claim 1, further comprising: receiving, fromthe network node, an address management message indicating a DN addressmanagement scheme, wherein identifying the DN address is based at leastin part on the DN address management scheme.
 22. The method of claim 1,further comprising: receiving, from the network node, an addressmanagement message indicating a forwarding information base (FIB) updatescheme; and updating a FIB based at least in part on the FIB updatescheme.
 23. The method of claim 1, further comprising: exchanging one ormore signaling messages between the network management function and thesecond relay.
 24. The method of claim 1, further comprising: determiningpacket forwarding rules based at least in part on the PDU sessionrequest forwarded from the second relay to the network managementfunction.
 25. The method of claim 1, wherein establishing the firstconnection to the first DN comprises: transmitting, to the network node,a radio resource control (RRC) connection request message; andreceiving, from the network node, an RRC response message.
 26. Themethod of claim 1, wherein the PDU session request indicates a networkname.
 27. The method of claim 1, wherein: the DN address comprises anaddress for an Internet Protocol (IP) network, an 802.1 local areanetwork (LAN), or a packet data network (PDN).
 28. An apparatus forwireless communication, comprising: means for establishing a firstconnection to a first data network (DN) via a wireless link with anetwork node; means for receiving, from a relay, a packet data unit(PDU) session request; means for forwarding the PDU session request to anetwork management function; means for identifying a DN address for therelay; means for establishing a second connection to a second DN for therelay; and means for connecting the relay to the first DN by routingdata from the first DN to the second DN based at least in part on theidentified DN address.
 29. An apparatus for wireless communication, in asystem comprising: a processor; memory in electronic communication withthe processor; and instructions stored in the memory and operable, whenexecuted by the processor, to cause the apparatus to: establish a firstconnection to a first data network (DN) via a wireless link with anetwork node; receive, from a relay, a packet data unit (PDU) sessionrequest; forward the PDU session request to a network managementfunction; identify a DN address for the relay; establish a secondconnection to a second DN for the relay; and connect the relay to thefirst DN by routing data from the first DN to the second DN based atleast in part on the identified DN address.
 30. A non-transitorycomputer readable medium storing code for wireless communication, thecode comprising instructions executable by a processor to: establish afirst connection to a first data network (DN) via a wireless link with anetwork node; receive, from a relay, a packet data unit (PDU) sessionrequest; forward the PDU session request to a network managementfunction; identify a DN address for the relay; establish a secondconnection to a second DN for the relay; and connect the relay to thefirst DN by routing data from the first DN to the second DN based atleast in part on the identified DN address.